Skip to content

Conversation

@mjcarroll
Copy link
Member

This will allow users to take multiple messages in one take call if they
are available in the underlying middleware, versus having to make
multiple rmw_take calls in a row.

Signed-off-by: Michael Carroll [email protected]

@mjcarroll
Copy link
Member Author

mjcarroll commented Apr 10, 2020

Covering all branches:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@mjcarroll mjcarroll force-pushed the take_sequeunce branch 2 times, most recently from f28532a to 3d7d7a3 Compare April 16, 2020 16:05
@mjcarroll mjcarroll requested a review from wjwwood April 16, 2020 16:12
Copy link
Member

@jacobperron jacobperron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some minor comments. LGTM

@mjcarroll mjcarroll force-pushed the take_sequeunce branch 2 times, most recently from 54667ff to 7453971 Compare April 20, 2020 19:33
@mjcarroll
Copy link
Member Author

CI incorporating all changes:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@mjcarroll
Copy link
Member Author

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@mjcarroll
Copy link
Member Author

Linux and macOS are failing with Connext patching issues, similar to here: ros2/rmw_connext#399 (comment)

Windows went green too quickly.

@mjcarroll
Copy link
Member Author

mjcarroll commented Apr 23, 2020

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@mjcarroll mjcarroll self-assigned this Apr 23, 2020
@mjcarroll
Copy link
Member Author

One more?

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

Copy link
Contributor

@Karsten1987 Karsten1987 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just out of curiosity, does it make sense to have a take_all or similar which takes all available messages at a certain timestamp? Or maybe another rmw method to get the amount of available methods per subscription so that the caller side can allocate the sequence appropriately?
Might be out of scope though.

mjcarroll and others added 8 commits April 23, 2020 16:55
This will allow users to take multiple messages in one take call if they
are available in the underlying middleware, verus having to make
multiple rmw_take calls in a row.

Signed-off-by: Michael Carroll <[email protected]>
Co-Authored-By: Jacob Perron <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Co-Authored-By: Jacob Perron <[email protected]>
Co-Authored-By: William Woodall <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
Signed-off-by: Michael Carroll <[email protected]>
@mjcarroll
Copy link
Member Author

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@mjcarroll
Copy link
Member Author

  • macOS rebuild Build Status

@mjcarroll mjcarroll merged commit 7703d74 into master Apr 24, 2020
@delete-merged-branch delete-merged-branch bot deleted the take_sequeunce branch April 24, 2020 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants